DevOps: VPC Module: Update NAT Gateway EIP configuration and add addiβ¦#24
Open
rxnjitth wants to merge 1 commit intoNotHarshhaa:masterfrom
Open
DevOps: VPC Module: Update NAT Gateway EIP configuration and add addiβ¦#24rxnjitth wants to merge 1 commit intoNotHarshhaa:masterfrom
rxnjitth wants to merge 1 commit intoNotHarshhaa:masterfrom
Conversation
β¦tional outputs for VPC resources
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue ID : #22
Summary
Added essential outputs to the VPC module for improved reusability and integration.
Changes
vpc_nameoutput for the VPC resource name.internet_gateway_idoutput for the IGW ID.public_route_table_idsandprivate_route_table_idsoutputs (lists for multi-AZ support).public_subnet_cidrsandprivate_subnet_cidrsoutputs (lists of CIDR blocks).nat_gateway_elastic_ipsoutput (list of EIP allocations for NAT GWs).All new outputs are derived from existing resources, ensuring no breaking changes to current consumers.
Why?
The module previously only exposed basic IDs, limiting visibility and ease of use in multi-module setups (e.g., passing route tables to security groups or CIDRs to EC2 modules). This enhances production flexibility across environments without disrupting existing workflows.
Testing